Managing building information and resolving building issues

ABSTRACT

In one implementation, a computer-implemented method includes receiving information that describes an issue with a building; accessing data that identifies (i) a plurality of components that are included in the building and (ii) features of the plurality of components; identifying one or more candidate components that have at least a threshold likelihood of being a cause of the issue; selecting a candidate service provider from among a plurality of service providers based on a comparison of (i) the one or more candidate components and (ii) information identifying technical qualifications for the plurality of service providers; transmitting a service request for the issue to the candidate service provider; receiving a response from the candidate service provider; and scheduling, based on the response, a service appointment with the candidate service provider to resolve the issue.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.16/201,560, filed on Nov. 27, 2018, now U.S. Pat. No. 10,657,610, whichis a Continuation of U.S. application Ser. No. 15/360,653, filed Nov.23, 2016, now U.S. Pat. No. 10,147,149, which is a Continuation of U.S.application Ser. No. 14/925,358, filed Oct. 28, 2015, now U.S. Pat. No.9,536,231, which claims the benefit of priority to U.S. ProvisionalApplication Ser. No. 62/069,559, which is entitled “MANAGING BUILDINGINFORMATION AND RESOLVING BUILDING ISSUES” and has a filing date of Oct.28, 2014; to U.S. Provisional Application Ser. No. 62/115,088, which isentitled “MANAGING BUILDING INFORMATION AND RESOLVING BUILDING ISSUES”and has a filing date of Feb. 11, 2015; to U.S. Provisional ApplicationSer. No. 62/172,697, which is entitled “MANAGING BUILDING INFORMATIONAND RESOLVING BUILDING ISSUES” and has a filing date of Jun. 8, 2015;and to U.S. Provisional Application Ser. No. 62/206,265, which isentitled “MANAGING BUILDING INFORMATION AND RESOLVING BUILDING ISSUES”and has a filing date of Aug. 17, 2015. The entire contents of theseapplications are incorporated herein by reference.

TECHNICAL FIELD

This document generally describes computer-based technology related tomanaging building information and resolving building issues.

BACKGROUND

Users have traditionally called service technicians to fix issues withintheir buildings (e.g., house, apartment, office). For example, a userwho notices that a component (e.g., sprinkler head) of a firesuppression system is leaking may call a service technician to come outto resolve the issue, which may involve replacing the leaky sprinklerhead. With regard to such issues, users have been responsible to managewarranties for various components that are included in buildings, suchas warranties covering materials (e.g., shingles, flooring materials),fixtures (e.g., lighting fixtures, plumbing fixtures), and appliances(e.g., washer, dryer, refrigerator).

SUMMARY

This document generally describes computer-based technology related tomanaging building information and associated warranties, triagingbuilding issues, and facilitating appropriate responses to such buildingissues. For example, this document describes computer systems that canobtain and manage information related to the components that areinstalled in a building, such as information identifying the particularcomponents that are installed, the dates on which they were installedand/or serviced, and their associated warranties and warranty periods.Such computer systems can additionally assist users in triaging andresolving issues that may arise with a building, such as light switchesnot working properly and/or fire suppression systems (e.g., sprinklersystems) malfunctioning. For instance, users can be guided through aprocess to identify specific components and systems within a buildingthat are malfunctioning, to determine whether the issue is currentlyunder warranty, and/or to determine a level of urgency for resolving theproblem. Such a process can additionally include identifying servicetechnicians qualified to resolve the issues with the appropriatecomponents within an acceptable timeframe based on the level of urgency.

In one implementation, a computer-implemented method includes receiving,at a computer system and from a client computing device, informationthat describes an issue with a building, the information including firstinformation corresponding to the issue and second informationidentifying the building or a user associated with the building;accessing, by the computer system and based on the second informationidentifying the building or the user associated with the building, datathat identifies (i) a plurality of components that are included in thebuilding and (ii) features of the plurality of components; identifying,by the computer system and based on a comparison of the firstinformation with the data for the building, one or more candidatecomponents that have at least a threshold likelihood of being, at leastpartially, a cause of the issue; selecting, by the computer system, acandidate service provider from among a plurality of service providersbased on a comparison of (i) the one or more candidate components and(ii) information identifying technical qualifications for the pluralityof service providers; transmitting, by the computer system, a servicerequest for the issue to the candidate service provider; receiving, atthe computer system, a response from the candidate service provider; andscheduling, by the computer system and based on the response, a serviceappointment with the candidate service provider to resolve the issue.

Such a method can optionally include one or more of the followingfeatures. The service request can include information identifying theone or more candidate components, and the response from the candidateservice provider can indicate that the one or more candidate componentsare currently accessible to the candidate service provider for theservice appointment. The service request can include informationidentifying a timeframe for resolving the issue, and the response fromthe candidate service provider can indicate that the candidate serviceprovider is currently able to resolve the issue within the timeframe.The computer-implemented method can further include determining a levelof urgency of the issue based on the information received from theclient computing device; and determining the timeframe based, at leastin part, on the level of urgency.

The candidate service provider can be selected based, at least in part,on the candidate service provider either providing a warranty associatedwith the one or more candidate components or being preapproved by awarranty provider for the one or more candidate components to servicethe issue. The candidate service provider can be selected using abidding process for the service request involving a plurality ofcandidate service providers, and the candidate service provider can beselected based, at least in part, on a particular bid that was providedby the candidate service provider for the bidding process. The bidprovided by the candidate service provider can have provided a lowestprice for servicing the issue from among all bids received in thebidding process. The bid provided by the candidate service provider canhave provided a shortest guaranteed timeframe for servicing the issuefrom among all bids received in the bidding process. The bid provided bythe candidate service provider can have provided a fastest guaranteedresponse time for servicing the issue from among all bids received inthe bidding process.

The information that describes the issue with the building can be one ormore photographs taken of the issue by the client computing device. Thecomputer-implemented method can further include transmitting componentinformation that describes the one or more candidate components to theclient computing device; and receiving, from the client computingdevice, selection of one or more of the candidate components as being alikely cause of the issue. The component information can be images ofthe one or more components. The component information can be textualdescriptions of where in the building the one or more components areinstalled. The computer-implemented method can further includedetermining whether the one or more candidate components are coveredunder one or more warranties; and transmitting information about the oneor more warranties to the client computing device. Thecomputer-implemented method can further include processing payment forwork performed at the service appointment based, at least in party, onthe one or more warranties for the one or more candidate components.

The computer-implemented method can further include receivinginformation from the candidate service provider indicating that theissue with the building has been resolved; transmitting, to the clientcomputing device, a request for confirmation that the issue has beenresolved; and receiving, from the client computing device, confirmationthat the issue has been resolved. The computer-implemented method canfurther include, in response to receiving the conformation from theclient computing device, processing payment of one or more invoices fromthe candidate service provider for work performed at the serviceappointment.

Other embodiments of these aspects include corresponding apparatus andcomputer programs recorded on one or more computer storage devices,configured to perform the actions of the methods. A system of one ormore computers can be configured to perform particular operations oractions by virtue of having software, firmware, hardware, or acombination of them installed on the system that in operation causes orcause the system to perform the actions. One or more computer programscan be configured to perform particular operations or actions by virtueof including instructions that, when executed by data processingapparatus, cause the apparatus to perform the actions.

The details of one or more implementations are depicted in theassociated drawings and the description thereof below. Certainimplementations may provide one or more advantages. For example, thedisclosed technology can help solve the technical problem of accuratelydiagnosing electrical and mechanical issues that arise within abuilding, especially when observed by a lay person. By storing and usingcomprehensive information regarding the components and systems that areincluded within a building, users (including non-expert users, such ashomeowners) can accurately evaluate an issue, identify specific systemsand components that are implicated as part of the issue, and determinethe source of the issue, the severity of the issue, and best steps forresolving the issue.

For example, a homeowner may not know details about the components oftheir fire suppression system, such as sprinkler heads, shutoff valves,and control panels, let alone how to determine whether an issue (e.g., awater leak) in their house is being caused by the fire suppressionsystem or other water systems within the home. The disclosed technologycan help such a homeowner, who may be a lay person, successfully andaccurately triage such issues. For instance, a homeowner who finds apool of water on the floor can use the disclosed technology toaccurately triage the system (e.g., fire suppression system) andspecific installed component (e.g., sprinkler head) that is causing theissue (e.g., water on the floor), all without the homeowner needingspecial knowledge about the systems or components within their home.

Such improved accuracy in triaging building issues can carry overadvantages to service providers and others (e.g., insurers, warrantyproviders, component/system manufacturers) by providing a more accurateand detailed initial report of the issue, the cause of the issue, andthe specific components installed. For example, the disclosed technologycan allow a user to, themselves, identify specific components (e.g.,make, model, serial number) that may be malfunctioning and in need ofrepair or replacement before a service technician has even received theservice request. Such information can help ensure that the servicetechnician shows up at the user's building with the proper tools andequipment to perform the needed service, as well as having anappropriate level of skill to perform the work and a sufficient amountof time blocked off to perform the service request. Such accurateinformation up-front can reduce the overall cost of processing servicerequests, which can benefit insurers, warranty providers, andcomponent/system manufacturers who may be paying for the resolution ofthe service request. Additionally, the accuracy of such information canassist in the efficient resolution of the building issue, which can inturn reduce the amount of damage that may be caused by the buildingissue and the overall cost to repair the damage.

In another example, the safety of users can be increased by helpingusers to determine the technical problem of whether a building issue ispotentially dangerous to the health and well-being of users who may belocated within or near the building. For example, it can often bedifficult for users to determine whether an issue within a building ispotentially dangerous. The disclosed technology can assist users inaccurately triaging building issues and can provide guidance as toappropriate steps to minimize any exposed danger, such as leaving thebuilding immediately, not turning any electrical switches on or off,and/or turning off the valve for the water main.

In a further example, the disclosed technology can assist users intracking and monitoring warranty information for systems and componentsthat are installed in a building. For instance, a new home will ofteninclude multitudes of individual components that may each have one ormore warranties, such as warranties from manufacturers, installers, andgeneral contractors/builders. Monitoring and tracking the periods andconditions for each of these warranties can be difficult. The disclosedtechnology can assist users in more accurately and easily monitoringbuilding warranties, renewing building warranties prior to expiration,and submitting/processing warranty claims.

Other features, objects, and advantages of the technology described inthis document will be apparent from the description and the drawings,and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual diagram of an example system for managingbuilding information and associated warranties, triaging buildingissues, and/or facilitating appropriate responses to such buildingissues.

FIG. 2 is a flowchart of an example technique for identifying buildingcomponents.

FIG. 3 is a diagram of an example system for managing and servicingbuilding components.

FIGS. 4A-B is a flowchart of an example technique for triaging andresolving issues in a building through a service request.

FIGS. 5A-Q are screenshots of an example mobile application that can beused by field service providers, such as builders, contractors, vendors,and other service providers.

FIGS. 6A-H are screenshots of an example mobile application that can beused to address building issues.

FIG. 7 is a diagram of an example workflow for an entity with multipledifferent departments that are used by the entity to schedule andprovide services to customers.

FIG. 8 is an architectural diagram of a mobile application andsupporting backend system for field service providers, such as builders,contractors, vendors, and other service providers.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 is a conceptual diagram of an example system 100 for managingbuilding information and associated warranties, triaging buildingissues, and/or facilitating appropriate responses to such buildingissues. The example system 100 includes a computer system 102 thatstores and uses information about buildings, such as the examplebuilding 104 (e.g., house, condo building/unit, apartment building/unit,office, garage, recreational facility), to assist users with issuesrelated to buildings and components included therein, such as thecomponents 106 (e.g., systems within the building (e.g., firesuppression system, water system, HVAC system, electrical system) and/orsubparts of such systems (e.g., fixtures, pipes, countertops, wallingmaterial, insulation, cabinets, appliances)). The computer system 102can obtain such information from builders, contractors, and/or vendors108 who have installed, replaced, and/or repaired the components 106within the building 104, and can use the information to help a buildingowner 110 to manage the building 104, such as through managingwarranties of all of the components 106 and triaging issues that maycome up within the building 104, such as one or more of the components106 malfunctioning. The computer system 102 can additionally interfacewith one or more other parties 112 (e.g., builders, contractors,vendors, service technicians, component manufacturers/warrantyproviders, insurers) to facilitate appropriate resolution of issues thatmay arise in the building 104.

For example, the building 104 can be a home that was built by a generalcontractor and a multitude of subcontractors (e.g., builders,contractors, and vendors 108) and the building owner 110 can be thehomeowner (or other person/entity associated with a building, such as arenter, a tenant, a property management company). Given the multitude ofcomponents 106 in the building 104 and the multitude of associatedwarranties, such as warranties from manufacturers, resellers, and/orcontractors, it can be difficult for the homeowner to keep track of allthis information for the building 104 and components 106. The computersystem 102 can simplify the process for the homeowner by providinginterfaces through which the builders, contractors, and vendors 108 canprovide information about the building 104 and its components 106 to thecomputer system 102, which can manage the information. The computersystem 102 can then provide the homeowner with access to theinformation, such as to allow the homeowner to view information aboutspecific components that are installed in the building 104. For example,the homeowner can remotely look-up appliance and fixture information forthe building 104. Additionally, the computer system 102 can use theinformation about the building 104 to assist the homeowner in accuratelytriaging issues (e.g., water leaks, appliances and/or fixtures notfunctioning properly) that arise in the home, based on the specificcomponents 106 that have been installed in the building 104.

For instance, it can often be difficult for a lay person to accuratelyidentify a type of component within their home (e.g., determiningwhether a valve is for the gas line or the water line), let alone toidentify more specific information about the components, such as thespecific make and model of the component, the age of the component,average life of the component, ways in which the component maymalfunction (e.g., a range of problems that may occur with thecomponent), common ways in which the component will malfunction (e.g.,particular parts that are likely to wear out before other parts of thecomponents), symptoms that indicate different types of malfunctioning ofthe component, warranties associated with the component, and/orappropriate service technicians to fix the component. The computersystem 102 can use the specific information about the components 106that are installed in the building 104 to assist the homeowner inaccurately identifying the source of a problem (e.g., a water leak) inthe building 104, the specific components that are likely the cause ofthe problem, likely resolutions of the problem (e.g., replacing orrepairing the specific components), the level of danger and/or severityof the problem, whether the problem is currently covered under one ormore warranties, and appropriate entities (e.g., service technicians,warranty providers) to contact to resolve the problem.

As indicated by step A (114), the builders, contractors, and/or vendors108 can transmit, using computing devices (e.g., desktop computer,tablet computing device, smartphone, laptop, wearable computing device)that are not depicted, information about the building 104 to thecomputer system 102. The computer system 102 can provide one or moreinterfaces through which the builders, contractors, and/or vendors 108can transmit the information, such as webpages and/or mobileapplications. The interfaces can include any of a variety of featuresthat can help facilitate entering and transmitting the information, suchas importing information from bills of materials, optically scanningbarcodes of components, using near field communication (NFC) devices(e.g., RFID tags) to obtain information about the components, and/orother data sources and/or devices that can reduce manual entry of theinformation. The information that is transmitted to the computer system102 can include component information 116 and warranty information 118.The component information 116 can include information that identifiesthe components 106, such as make and model information, serial numbers,other unique identifiers (e.g., barcodes) for the components 106, and/orinformation about how and/or by whom the component wasinstalled/serviced/repaired. The warranty information 118 can includeinformation that identifies warranties for the components, such as awarranty provider, terms and conditions on the warranty, warrantyperiods, authorized parties for servicing the warranty, and/or warrantyrenewal information.

The information 116 and 118 that is transmitted for the example building104 at step A (114) can be transmitted by one or more parties. Forexample, subcontractors working under the direction of a generalcontractor constructing the building 104 can each individually transmitappropriate information for the portion of the building 104 that theyhave constructed. In another example, such a general contractor mayitself submit all of the information for the building 104. Submissionsof information may occur over time for the building 104 (e.g., asdifferent stages of construction/installation are completed, asdifferent services/repairs are performed) or all at once (e.g., uponcompletion of the construction of the building 104).

The computer system 102 (e.g., computer server system, cloud-basedcomputing system, desktop computer, laptop computer, tablet computingdevice, smartphone) can receive the information 116 and 118 that istransmitted by the builders, contractors, and vendors 108 and, asindicated by step B (120), can store the building information. Forexample, the computer system 102 can store the information in one ormore data repositories 122 a-c (e.g., databases, file systems), such asa building data repository 122 a, an entity data repository 122 b, anowner data repository 122 c, and/or other appropriate data repositories.The building data repository 122 a can store information regarding thebuilding 104, such as information about the building 104 (e.g., address,type of building, date of construction, unique identifier for thebuilding), information about the components 106 (e.g., the componentinformation 116, the warranty information 118), and/or other appropriateinformation. The entity data repository 122 b can store informationabout the builders, contractors, and vendors 108, as well as informationabout the other parties 112, such as contact information for the entity(e.g., name, telephone number, fax number, email address, uniqueidentifier for the entity), information identifying specialties andother ways in which the entities are associated with buildings and theircomponents (e.g., builder, installer, manufacturer, warranty provider,insurer), account information on the computer system 102 for theentities (e.g., username, password), and other appropriate information.The owner data 122 c can include a variety of information about theowner 110 of the building 104, such as the owner's name and contactinformation, buildings that the owner is associated with, accountinformation (e.g., username, password), and other appropriateinformation for the owner 110.

Once stored, the computer system 102 can maintain and manage thecomponent information 116 and the warranty information 118, such as parta subscription service that is offered over a period of time or forperpetuity on behalf of the builders, contractors, and/or vendors 108who built the building 104 and/or installed/repaired components 106 inthe building 104. Such management can include providing the owner 110with access to information about the building 104, such as component andwarranty information. Additionally, the management can include providingthe owner 110 with reminders about warranty periods, upcoming warrantyexpirations, obtaining quotes from one or more warranty providers forextended warranties, and/or facilitating the purchasing and managementof extended warranties. Additionally, as described below with regard tosteps C-N, the computer system 102 can assist the owner 110 in triagingand resolving issues that may arise with the building 104 and/or itscomponents 106.

Such services can be provided to the owner 110 (and/or the builders,contractors, vendors 108 and/or the other parties 112) on one or morebases, such as through subscriptions to the services provided by thecomputer system 102. For example, a builder that builds a building(e.g., a new home) may cover the cost of a subscription to the serviceprovided by the computer system 102 for the building 104 for a period oftime (e.g., 1 year, 3, years, 5 years, 10 years, 15 years) on thebuilding owner's behalf and after that period of time, the owner maybecome responsible for the subscription fee. In another example,building owners may sign-up for the service provided by the computersystem 102 on their own.

Regarding triaging issues that may arise with the building 104 and/orits components 106, the owner 110 can use his/her computing device 124(e.g., laptop, tablet computing device, smartphone, wearable computingdevice) to transmit initial information about an issue in the building104, as indicated by step C (126). Such issues can include a variety ofdifferent things that may be malfunctioning or otherwise problematicwith the building 104 and/or the components 106, such as breakage,leaks, items becoming discolored and/or wearing out, and/or appliancesnot functioning properly.

This initial transmission can be made through one or more interfacesthat are presented on the computing device 124, such as through awebpage that is downloaded onto the computing device 124 from thecomputer system 102, an application (e.g., mobile application) that isinstalled and running on the computing device 124, and/or one or morecommunication/messaging features (e.g., telephone call, videoconference, text message, chat session) that are provided on thecomputing device 124.

As indicated by step D (128), the computer system 102 can receive theinformation describing the issue from the owner 110 and can, based onthe information, identify one or more of the components 106 ascandidates for being a source of the issue. For example, the owner 110may indicate that they have noticed a water leak from the ceiling in aparticular room in the building 104. The computer system 102 canreference the components 106 that are installed in the building 104 fromthe building data repository 122 a to identify possible componentsand/or systems that may be causing the water leak in the particularroom. For instance, the computer system 102 can identify components ofwater systems within the building 104, such as domestic water systems(e.g., domestic water lines and components, waste water lines andcomponents) and fire suppression systems (e.g., sprinkler systems andcomponents) as candidate components that may be causing the examplebuilding issue (water leak).

Such identification can be made by the computer system 102 based on oneor more of a variety of appropriate factors, such as the type of issue(e.g., water, electrical, appliance, HVAC, interior, exterior),classifications of the components 106 (e.g., water system component,electrical system component, appliance, HVAC component, interiorcomponent, exterior component), information identifying a locationwithin the building 104 where the issue exists (e.g., kitchen, bathroom,garage, basement), locations within the building 104 where thecomponents 106 are located (e.g., particular room(s) where thecomponents 106 are located), and/or process flows/algorithms that may beused to identify candidate components that may be implicated as part ofthe issue.

Also as part of step D (128), the computer system 102 can additionallyidentify one or more warranties that are associated with the candidatecomponents. For example, the computer system 102 can identify candidatecomponents and their associated warranties as they apply to the building104 from the building data 122 a. For example, in response to thebuilding owner 110 indicating that the building 104 is experiencingwater leaks in the kitchen of the building 104, the computer system 102can identify the kitchen faucet, the refrigerator with built-inice/water dispenser, a fire suppression system with sprinkler heads inthe kitchen, and an adjacent bathroom with a faucet and toilet ascandidate components. The computer system 102 can additionally identifycurrent warranty coverage for these components as they are installed inthe building 104. For example, the kitchen faucet may be still under amanufacturer's warranty whereas a manufacturer's warranty for therefrigerator may have expired.

As indicated by step E (130), the computer system 102 can then transmitinformation regarding the identified candidate components and associatedwarranties to the computing device 124 for the building owner 110. Theinformation that is transmitted to the computing device 124 can includetextual, visual, and other information that can help the building owner110 correctly identify components in the building 104. For example, theinformation that is transmitted can include images of the candidatecomponents, descriptions of where these components can be found, andmarking information for the candidate components that can help verifycorrect identifications.

As indicated by step F (132), the computing device 124 can output theinformation regarding the candidate components and associatedwarranties. For example, the computing device 124 can be a mobilecomputing device, such as a smartphone or tablet computing device, thatis running a mobile application (“mobile app”) that can receive theinitial user input regarding the building issue (step C-126), transmitthe information to the computer system 102, and then in response canreceive and output the information regarding the candidate componentsand warranties. For instance, images and descriptions of the candidatecomponents can be displayed on the computing device 124 and can beselected by the building owner 110.

In some implementations, the computer system 102 can transmitinformation to the computing device 124 that can be used by thecomputing device 124, such as by a mobile app running on the computingdevice 124, to provide an interface that identifies the candidatecomponents within the building 104. For example, the mobile app runningon the computing device 124 can include an augmented reality featurethat highlights the candidate components on a display of the computingdevice 124 in near real-time. Such a feature can help a userappropriately identify the components within the building 104 that aremalfunctioning or otherwise in need of service.

Referring to FIG. 2, for example, a flowchart of an example technique200 for identifying building components is depicted. The exampletechnique 200, for example, can be performed by the computer system 102,and/or by the computing device 124. A user interface can be provided bythe computing device 124 to output the candidate component and warrantyinformation, and to receive user selection of one or more of thecandidate components as the source of the issue and to receive userinput regarding other associated information (e.g., further descriptionof the issue and the problem with the components, availability forservice repairs). Such a user interface can be one or more appropriateuser interfaces, such as graphical user interfaces (GUI), voice userinterfaces, gesture/movement based user interfaces, or any combinationthereof. Techniques other than the example technique 200 can beperformed to triage building issues and to identify building components.

At 210, the computer system 102 can receive visual information for anunidentified component from the computing device 124. For example, thecomputing device 124 can provide a photo or video file, and/or areal-time video stream of a component within the building 104 that ismalfunctioning or otherwise in need of service. For instance, thecomputing device 124 can provide an interface, such as a touchscreeninterface on a mobile computing device, through which a user cantake/select a picture, video, audio recording, and/or other mediarepresenting a component.

At 220, the computer system 102 can optionally receive locationinformation for the unidentified component from the computing device124. For example, the computing device 124 can provide locationinformation corresponding to a location within the building 104, such asinformation identifying a room selection by a user, GPS (GlobalPositioning System) data for a current location selected by a user ofthe computing device 124, wireless beacon signal information (e.g.,information identifying nearby wireless transmitters, like WiFi routersand BLUETOOTH enabled devices) identifying nearby wireless beacons andtheir corresponding signal strengths (which can identify a locationwithin a building), altimeter information identifying a current altitudefor the computing device 124 (which can indicate a floor within abuilding where the computing device 124 is located), digitalcompass/orientation sensors data (which can indicate a direction thatthe computing device 124 is facing/oriented towards), motion sensor data(which can identify movements resulting in the computing device 124'slocation). The location information provided by the computing device 124can be provided to the computer system 102, which can use the locationinformation to identify a location for the component.

At 230, based on the visual information for the unidentified componentand based on the optional location information for the unidentifiedcomponent, the computer system 102 can determine one or more candidatecomponents that have at least a threshold probability of being thecomponent identified (e.g., photographed) by the computing device 124.For example, the computer system 102 can determine candidate matchingcomponents using the building data 122 a and based one or more matchingtechniques (e.g., image recognition techniques, pattern matchingtechniques) scoring the candidate components along one or moredimensions (e.g., visual similarity to the target component, locationsimilarity, function similarity). For instance, the computer system 102can compare the received visual information to visual information (e.g.,pictures, videos, 2D/3D models) for candidate components to determine avisual matching score for each of the candidate components; the receivedlocation information with location installation information thatidentifies where each of the candidate components were installed in thebuilding at issue to determine location matching scores; and/or otherreceived information (e.g., information identifying an issue with thecomponent, like a water leak, smoke, smell, etc.) with informationdescribing categories and/or attributes of the candidate components(e.g., type of component, range of potential issues associated withcomponent, most common issues with component) to determine additionalmatching scores. The different scores can be combined (e.g., averaged,median, weighted average based on reliability of different scores,weighted average based on quality of information from the clientcomputing device (e.g., low image quality can weigh visual matchingscore lower than other matching scores, low accuracy in locationinformation can weigh location matching scores lower) and used toidentify components near the location within the building 104 identifiedat 220.

At 240, the computer system 102 can provide component identificationinformation for presentation by the computing device 124 for each of thecandidate components that have been identified as potentially matchingthe unidentified component visually captured by the computing device124. For example, the computing device 124 can provide a set of stockimages of candidate components, and optionally, additional descriptiveinformation (e.g., product information, location where the componentswere installed in the building at issues, troubleshooting information)for each of the candidate components. In some implementations, thecomputing device 124 can provide a visual indication of a candidatematching component that corresponds to an unidentified componentvisually captured by the computing device 124. For example, an augmentedreality feature of the computing device 124 can highlight anunidentified component corresponding to a potentially matching componenton a display of the computing device 124 in near real-time.

At 250, the computer system 102 can receive a selection of a matchingcomponent from the computing device 124. For example, based on the setof stock images and/or additional descriptive information, a user (e.g.,building owner) can identify a candidate component as the component thatis implicated in the issue with the building 104.

Referring again to FIG. 1, for example, the building owner 110 canprovide input identifying which of the candidate components is/areimplicated in the issue with the building 104 and, as indicated by stepG (134), the computing device 124 can transmit information regarding theowner's confirmation of the component(s) and further information aboutthe issue with the building 104 to the computer system 102. Thisinformation can be provided to the computer system 102 so that thecomputer system 102 can take appropriate steps to resolve the issue withthe building 104.

As indicated by step H (136), the computer system 102 can use thecomponent and building information that is provided by the computingdevice 124 to further triage the issue with the building 104. Suchtriaging can include identifying possible problems with the componentthat may be causing the problem and a range of potential solutions,which may include repairing or replacing the component as well asrelated components. For example, a leaky sprinkler head (examplecomponent confirmed by the building owner 110) that is part of a firesuppression system may, in some instances, simply need to be adjustedbut in other instances may need to be replaced.

The triaging can also include determining an appropriate timeframe toresolve the issue, which can be determined based on a level ofurgency/severity of the issue as well as other risks associated with theissue. For example, a water leak may be categorized as an urgent issuein need of immediate resolution because of the high potential for theissue to cause extensive damage to the building 104 if left unresolved.In another example, a malfunctioning fire alarm may also be identifiedas being urgent based on the lack of appropriate fire detection placingboth occupants of the building 110 and the building 110 itself at greatrisk.

The triaging can further include identifying candidate parties toresolve the issue within the appropriate timeframe. Such candidateparties may be parties (e.g., companies, individual workers,contractors) who are preapproved to service the issue under one or morewarranties that are covering components that are likely the source ofthe issue, such as parties who manufactured and/or installed thecomponents. For example, for issues that have been identified as beingurgent, the computer system 102 can attempt to identify parties, such asservice technicians and other skilled workers, who are available toperform the work within the appropriate timeframe and who have thecomponents that may be needed to resolve the issue. For instance, thecomputer system 102 can send out service requests to candidate partiesregarding the issue, components involved, and requested timeframe forresolution. Based on responses that are received, the computer system102 can then award the service request to one or more of the candidateparties. Such a process of soliciting candidate parties is depicted anddescribed with regard to steps I-K below.

The triaging may also include the computer system 102 identifying one ormore actions that the building owner 110 can take to mitigate furtherdamage and/or risk from the issue before a service technician or otherappropriate party is able to respond to and resolve the issue. Forexample, in the case of a water leak, the computer system 102 mayinstruct the building owner 110 to shut off the main water supply to thebuilding 104. Such instructions can draw from the building data 122 afor the building 104, and can be customized to the building 104 and theparticular issue. For instance, the instructions that are sent to thecomputing device 124 may include a description of where the buildingowner 110 should go within the house to the resolve the issue andpictures of components, such as a water shutoff valve, that the owner110 can use to mitigate the issue. Although not depicted in FIG. 1, suchinstructions can be output on the computing device 124 in a similarmanner to the user interface outputting information about the candidatecomponents and warranty information.

As indicated by step I (138), the computer system 102 can automaticallyengage appropriate entities, such as the other party 112, to helpresolve the issue with the building 104 within the appropriatetimeframe, as determined by the computer system 102. Such engagement caninclude transmitting service requests (and/or other requests), asindicated by step I (138), to a computing device 142 (e.g., laptopcomputer, mobile computing device (e.g., smartphone, tablet computingdevice), desktop computer, computer server system) that is associatedwith the other party 112. As discussed above, the other party 112 may bethe same as or different from the builders, contractors, and vendors108. For example, the other party 112 can be a company (e.g.,subcontractor) that installed the components or a company (e.g., generalcontractor, builder) that directed/oversaw the installation of thecomponents that are causing the issue in the building 104. In anotherexample, the other party 112 can be an entity or entities that mayprovide warranties for the components that are at issue, such asmanufacturers, installers, and/or other warranty providers.

The request 138 can include one or more pieces of information that arerelevant to the other party 112 evaluating and responding to the servicerequest. For example, example information 140 a-d that is depicted asbeing provided with the request 138 includes issue information 140 athat describes the issue at the building 104 (e.g., informationdescribing a water leak that has been detected in the kitchen of thebuilding 104, information specifying the requested timeframe forresolving the issue), component information 140 b that describes thespecific components that may need to be repaired and/or replaced as partof resolving the issue (e.g., product make and model for the components,quantities of the components, locations in the building 104 where thecomponents are installed and systems within which the components arebeing used), building information 140 c that describes the building 104(e.g., location of the building, type of building, building history,such as the year it was built and dates on which services have beenperformed), and/or pricing information 140 d that indicates one or moreprices that are being offered to service the issue at the building 104(e.g., approved reimbursement rate under one or more associatedwarranties, information indicating that the other party 112 isresponsible for servicing the issue at its own expense under one or moreassociated warranties).

In some implementations, the service request 138 can be provided tomultiple other parties 112. For example, the service request 138 can beprovided as part of a bidding process in which the other parties 112submit bids to perform the requested service at the building 104 and thecomputer system 102 can select one or more of the other parties 112 toperform the service based at least in part on the bids. Bidding can bebased on any of a variety of parameters, such as cost, estimated time tocompletion of the service (e.g., able to complete service the same day,within two days, within two weeks), estimated time to arrive at the jobsite to begin performing the service (e.g., proximity to the job site,availability to travel to the job site), current stock of and/or abilityto obtain the component (e.g., whether the other party currently has thecomponent or parts to repair the component in stock, whether the otherparty is able to readily obtain the component or repair parts), and/orother appropriate parameters. For example, even though the componentsthat need servicing at the building 106 may be covered under warranty,the warranty provider may be interested in servicing the warranty forthe lowest price possible. The computer system 102 can send out theservice request 138 on behalf of the warranty holder to multiple otherparties 112 to obtain bids from the other parties who are able toresolve the issue at the building 104 within the appropriate timeframedetermined by the computer system 102. For all bids received during thebidding period, which may range from a short period of time (e.g., 15minutes, 30 minutes, 1 hour, 6 hours) to longer periods of time (e.g., 1day, 3 days, 1 week), the computer system 102 can evaluate the bids andcan select one or more of the other parties 112 to service the requestbased on the bids.

As indicated by step J (144), the computing device 142 of the otherparty 112 can output information regarding the service request from thecomputer system 102. For example, the computing device 142 can be atablet computing device running a mobile app that displays the servicerequest and the associated information 140 a-d, and also providesfeatures through which the other party 112 can transmit a response tothe computer system 102.

As indicated by step K (146), the computing device 142 of the otherparty 112 can transmit an acceptance of the service request to thecomputer system 102. The acceptance can include any of a variety ofappropriate details, such as estimated timing information 148 a thatprovides an estimate as to when the service can begin and the durationof the service, pricing information 148 b that provides a pricequote/estimate for the other party 112 to perform the service at thebuilding 104, and/or location information 148 c (e.g., GPS coordinates,zip code, street address, city and state, route information) thatidentifies the current location of the person or group of people who aregoing to be travelling to the building 104 to perform the service. Otherinformation can also be provided to the computer system 102, such asinformation that identifies one or more people who are associated withthe other party 112 and who will be servicing the issue at the building104, such as workers within a company (e.g., plumbers working for aplumbing company) and/or subcontractors. Such information can be used toestablish communication with these other people so that the computersystem 102 can obtain updates from these other people, which canadditionally be provided to the building owner 110 and other interestedparties (e.g., warranty providers, insurers).

The computing device 142 can periodically (e.g., every 5 second, every10 minutes, every hour, every day) provide updates of the information148 a-c after initially responding and until the issue at the building104 has been resolved. For example, a mobile app that is running on thecomputing device 142 can provide an initial acceptance of the servicerequest at the building 104, and can thereafter provide updates as tothe location 148 c of the other party 112 and estimates of the time tostart/completion 148 a as well as the pricing information 148 b.

As indicated by step L (150), the computer system 102 can transmitinformation 152 a-b regarding the service request to the computingdevice 124 of the building owner 110. The information 152 a-b caninclude a variety of details regarding the service request and/or theother party who will be resolving the issue at the building 104, such asthe timeframe 152 a for resolution of the issue and information 152 bregarding the other party 112. The timeframe information 152 a caninclude information similar to the estimated timing information 148 a,such as information indicating when the other party 112 will arrive atthe building 110, an expected duration of the work, and/or an expectedtime when the work will be completed and the issue will be resolved. Theinformation 152 b can a variety of information about the other party112, such as the name and contact information for the other party 112,training and experience level of the other party 112, particularly withregard to the issue at the building 104, current location of the otherparty 112, reviews of the other party 112 by other users, and/or priceestimates (e.g., total price estimate, information indicating portionsof the price estimate that will be the responsibility of the buildingowner 110 under one or more warranty or insurance plans, informationindicating that the other party 112 is approved to provide service underthe warranty for the components) for the other party 112 to service therequest. Similar to step F (132), the information regarding the servicerequest can be output by the computing device 124, such as on a mobileapp.

The computing device 124, such as through a mobile app, may provide thebuilding owner 110 with features through which the building owner 110can further customize the service on the building 104, such asrequesting a particular time for the service provider to arrive at thebuilding 102 and/or requesting a different or specific service provider(e.g., someone other than the other party 112). Such requests can betransmitted back to the computer system 102, and can trigger additionalcommunication with the other party 112 or other people/companies,similar to the communication in steps I-K.

Through the computing device 124 and applications (e.g., mobile app, webbrowser) running thereon the building owner 110 can additionally providereviews of the work being performed on the building and can confirmwhether the issue with the building 104 has been resolved by the otherparty 112. For example, a user interface can be provided on thecomputing device 124 through which the building owner 110 can provide arating for the other party 112 with regard to one or more factors (e.g.,timeliness, professionalism, ability to effectively resolve the issue)and can confirm that the issue has been resolved. Such features may onlybecome available on the computing device 124 of the building owner 110after the other party 112 has indicated that their work on the building110 has been completed, confirmation of which can be transmitted to thecomputer system 102 by the computing device 142. Such reviews that areprovided upon completion of the work can provide more succinct andaccurate information about the other party 112, which may be used by thecomputer system 102 when soliciting and/or selecting parties to servicebuilding issues in the future.

As indicated by step M (154), the computing device 124 can transmitconfirmation that the service has been completed and the issue has beenresolved (along with other information, such as reviews of the otherparty 112) to the computer system 102.

As indicated by step N (156), the computer system 102 can process andstore information about the service request. Such processing can includedetermining who is responsible for reimbursing the other party 112 forthe services and parts used, and also determining an appropriate rate ofreimbursement. For example, the computer system 102 can determinewhether one or more warranty providers and/or insurers are responsiblefor payment of the other party 112, and/or an extent to which thebuilding owner 110 is responsible for some or all of the costs. Thecomputer system 102 can include e-commerce features that canautomatically invoice, obtain payment consents, and electronicallyprocess payments (e.g., credit card payments, electronic fund transfers)for the services with the appropriate parties.

The computer system 102 can additionally store the information regardingthe service request, such as the date on which the service wasperformed, the cause of the issue identified by the building owner 110as determined by the other party 112 providing the service, componentsthat were verified to be problematic, actions that were performed (e.g.,test/diagnose issue, review product/training manual on issue, repaircomponents) by the other party 112 to resolve the issue, costs forresolving the issue, the time it took to resolve the issue (e.g., timefor the other party 112 to arrive at the building, time to resolve theissue once at the building 104), reviews of the other party 112, and/orinformation identifying new components/parts that were installed in thebuilding 104. Such information can be stored in one or more datarepositories, such as the building data 122 a. This information can becombined with similar information from other service calls for the sameor other buildings, and can be used to provide analytics to any of avariety of entities, such as to the builders, contractors, and vendors108, to manufacturers, to insurers and/or warranty providers, and/or toother parties (e.g., the other party 112). For example, analytics can beprovided to builders, contractors, and vendors 108 indicating whichcomponents and systems building owners are having problems with, whenthe issues that are reported are a result of componentmalfunction/failure vs. user error, and/or the timeframe within whichthese issues are arising. Such information can be helpful to thebuilders, contractors, and vendors 108 so as to better inform them ofwhich components and systems to select for future projects, gaps ineducation of systems to building owners, and appropriately prices andlengths of time for warranties. Such analytics can be provided using anyof a variety of appropriate techniques, such as machine learningtechniques (e.g., neural networks, clustering, regressions, decisiontrees) that can identify correlations and associations across large datasets, such as correlations that can indicate that particular componentsare faulty.

FIG. 3 is a diagram of an example system 300 for managing and servicingbuilding components. The example system 300 includes an example computersystem 302, an example building owner computing device 304, an examplebuilder/contractor computing device 306, an example other partycomputing device 308, and an example network 310. The computer system302 can be similar to the computer system 102 described above withregard to FIG. 1 and can manage component and warranty information forbuildings, and can assist with triaging issues with buildings andresolving such issues. The building owner computing device 304 can besimilar to the computing device 124 described above with regard to FIG.1, and can be used by building owners (or other people who areresponsible for or work/live in a building) to identify and resolveissues in buildings. The builder/contractor computing device 306 can beused by builders, contractors, and vendors (or others who installcomponents within buildings) to provide details about components andsystems that are installed within buildings. The other party computingdevice 308 can be similar to the computing device 142 described abovewith regard to FIG. 1 and can be used to respond and fulfill servicerequests.

The computer system 302 can be any of a variety of appropriate systemsincluding one or more computing devices, such as computer servers,desktop computers, laptop computers, mobile computing devices, cloudcomputing systems, and/or other appropriate computing devices/systems.The computing devices 304-308 can be any of a variety of appropriatemobile computing devices, such as smartphones (e.g., IPHONE, ANDROIDsmartphones), cell phones (e.g., feature phones), tablet computingdevices (e.g., IPADs, ANDROID tablets), personal digital assistants(PDAs), computing devices embedded within vehicles (e.g., in-vehiclecomputer systems with displays and/or user interfaces built into thevehicles' consoles, vehicle mounted computing devices, golf carts withembedded computing devices), wearable computing devices (e.g., GOOGLEGLASS), laptop computers, netbook computers, and/or other appropriatemobile computing devices. The computer system 302 and the computingdevices 304-308 can communicate with each other over the network 310,which can be any of a variety of appropriate communication networks,such as the internet, mobile data networks (e.g., 3G/4G mobile datanetworks), wireless networks (e.g., Wi-Fi networks, BLUETOOTH networks),local area networks (LANs), wide area networks (WANs), virtual privatenetworks (VPNs), fiber optic networks, cellular networks, and/or anycombination thereof.

The computer system 302 is depicted as including a frontend 312 thatreceives, processes, and responds to requests from client devices, suchas the computing devices 304-308. The frontend 312 can include one ormore processes that receive communications over the network 310 on oneor more network ports, such as a webserver process and/or a mobileapplication backend process.

The computer system 302 further includes a building information module314 that is configured to obtain building information from clientcomputing devices, such as the builder/contractor computing device 306,and to store the information in one or more data repositories 324 a-d,such a building data repository 324 a that stores building and componentinformation similar to the building data repository 122 a describedabove with regard to FIG. 1.

The builder/contractor computing device 306 can obtain and provide suchbuilding information to the building information module 314 over thenetwork 310 through the use of its input subsystem 326, its outputsubsystem 328, and the one or more applications 330 that are installedon the device 306, such as a component and warranty application 332. Theinput subsystem 326 can include one or more appropriate input devicesthrough which a user of the device 306 can provide input, such as atouchscreen, physical buttons/keys, microphones, cameras, and/or otherappropriate input devices (e.g., accelerometers, gyroscopes). The outputsubsystem 328 can include one or more appropriate output devices throughwhich information can be provided to a user, such as a display,speakers, haptic feedback devices (e.g., vibration device), and/or otherdevices that are in communication with the device 306 (e.g., wirelessheadset). The applications 330 can be of any of a variety of appropriatetypes, such as software (e.g., mobile app), hardware (e.g., applicationspecific integrated circuit (ASIC)), and/or firmware. The component andwarranty application 332 can be programmed to obtain information aboutcomponents that have been installed in buildings through, for example,the input subsystem 326 (e.g., bar code scan using a camera, typedinput) and/or data sources (e.g., document including a bill ofmaterials) that are accessible to the device 306, and to transmit suchinformation to the computer system 302 over the network 310.

The computer system 302 further includes a building issue module 316that is programmed to triage building issues that are raised by users,such as a user associated with the building owner computing device 304.The building issue module 316 is programmed to receive issues that areidentified by users, to identify specific candidate components that areinstalled in the buildings that are associated with the issues (e.g.,through referencing the building data repository 324 a and owner data324 c), to transmit information (e.g., images, description of wherecomponents installed in specific building) about the candidatecomponents to the users' computing devices (e.g., device 304), toreceive further clarifying input from users regarding issues, and toidentify one or more components that are likely causing the buildingissues. As described above with regard to step H (136), the buildingissue module 316 can additionally be programmed to determine levels ofurgency for building issues, to determine appropriate timeframes forresolution, and to provide users with recommended steps for mitigatingfurther damage and/or danger within their buildings as result of theissues.

The building owner computing device 304 can provide such informationabout building issues to the computer system 302 through the use of aninput subsystem 334 (can be similar to the input subsystem 326), anoutput subsystem 336 (can be similar to the output subsystem 228), andone or more applications 338 that are installed on the device 304, suchas a building issue application 340 and/or a service request application342. Similar to the applications 330, the applications 338 can beimplemented on the device 304 as software, hardware, and/or firmware.The building issue application 340 can include interfaces that guide auser through appropriately identifying the issue that the user isattempting to resolve, including categorized groupings of components andissues, images of components that are installed in the building, and/ortaking images of components using cameras that may be part of the inputsubsystem 334. The service request application 342, which can be part ofor separate from the building issue application 340, can facilitatescheduling, managing, and reviewing service requests.

The computer system 302 further includes a warranty module 318 that isprogrammed to determine whether building issues and components that areassociated therewith are covered under one or more warranties, such as amanufacturer's warranty. The warranty module 318 can be used by thecomputer system 302 to identify which entity is financially responsiblefor resolving building issues that are raised by users.

The computer system 302 further includes a service request manager 320that is programmed to facilitate and manage service requests that areused to resolve building issues that are raised by users, such as bycommunicating with service providers, warranty providers, and/orinsurers. The service request manager 320 includes several subcomponents322 a-c, including a bidding module 322 a that is configured to solicitand manage bidding processes for service requests, a payment processor322 b that is configured to identify and bill appropriate entities(e.g., building owner, warranty provider, insurer) for work performed,and a communication module 322 c that is configured to managecommunication with all entities associated with service requests, suchas building owners (e.g., computing device 304), builders/contractors(e.g., computing device 306), and/or service and warranty providers(e.g., computing device 308).

The computer system 302 can use one or more data sources 324 a-d, suchas a building data source 324 a that can store information aboutbuildings (e.g., component information), a contractor data source 324 bthat can store information about contractors/builders/vendors/serviceproviders, an owner data source 324 c that can store information aboutbuilding owners, and a service request data source 324 d that can storeand log information about both completed and pending service requests.

Like the computing device 142 described above with regard to FIG. 1, theother party computing device 308 can be associated with any of a varietyof entities that may be involved with service requests, such as serviceproviders (e.g., builders, contractors, vendors), componentmanufacturers, warranty providers, and/or insurers. In some instances,the computing device 306 is the same as the computing device 308 (e.g.,builder of home is also the service provider on a service request forthe home). The service request manager 320 can communicate with theother party computing device 308 with regard to service requests, suchas with regard to bid requests and service requests that have beenassigned to the associated other party. Like the computing devices 304and 306, the computing device 308 includes an input subsystem 344, anoutput subsystem 346, and one or more applications 348, such as abidding application 350 that is programmed to process and respond to bidrequests and a service request application 352 that is programmed tomanage and facilitate the fulfillment of service requests. The biddingapplication 350 and the service request application 352 can be part ofthe same or different applications.

FIGS. 4A-B depict a flowchart of an example technique 400 for triagingand resolving issues in a building through a service request. Theexample technique 400 is depicted as being performed by a building ownercomputing device 402, a builder/contractor computing device 404, acomputer system 406, and another party computing device 408. Thebuilding owner computing device 402 can be any of a variety ofappropriate computing devices, such as the computing device 124 and/orthe computing device 304. The builder/contractor computing device 404can be any of a variety of appropriate computing devices, such as thecomputing device 306. The computer system 406 can be any of a variety ofappropriate computer systems, such as the computer system 102 and/or thecomputer system 302. The other party computing device 408 can be any ofa variety of appropriate computing devices, such as the computing device142 and/or the computing device 308.

At 410, the builder/contractor computing device 404 can receive userinput about component and warranty information in a building. Thebuilder/contractor computing device 404 can transmit the component andwarranty information to the computer system 406 (412), which can receiveand store the component and warranty information (414).

The building owner computing device 402 can receive user input aboutissues in the building for which the component and warranty informationwas stored (416) and can transmit the initial information about thebuilding issue to the computer system 406 (418).

The computer system 406 can receive the initial information and, basedon the initial information and the stored component information for thebuilding, can identify candidate components that may be causing orotherwise impacted by the issue (420). The computer system 406 cantransmit information about the candidate components back to the buildingowner computing device 402 (422).

The building owner computing device 402 can receive and outputinformation about the candidate components (424) and receive furtheruser input clarifying the building issue based on the candidatecomponents (426), such as the user selecting one or more components fromthe candidate components as being the cause of the building issue. Thebuilding owner computing device 402 can transmit information about theclarified building issue, such as the user selected components, to thecomputer system 406 (428).

The computer system 406 can receive the additional building issueinformation (430) and can triage the building issue based, at least inpart, on building issue information (initial and additional information)and the previously uploaded information about the components in thebuilding and their associated warranties (432). The triaging can includeany of a variety of appropriate steps, such as identifying additionalcomponents that may be related to the issue and that may not have beenidentified by the user (434), determining warranty coverage for thebuilding issue (436), determining a level of urgency/emergency for thebuilding issue (438), and identifying candidate parties to service thebuilding issue (440).

With candidate parties identified, in some implementations the computersystem 406 can request and receive bids to perform a service request toresolve the building issue (442). For example, the computer system 406can send a request for bids to one or more candidate parties (e.g.,builders, contractors, vendors), such as the entity associated with theother party computing device 408 which can receive the request andrespond with one or more bids (446). With the bids received, thecomputer system 406 can evaluate the bids and select one or more winningbids to service and resolve the building issue (448).

The computer system 406 can then transmit a formal service request forthe building issue to one or more entities that either won a biddingprocess or that were otherwise selected by the computer system 406, suchas during the triaging (450). The formal service request can include avariety of details regarding the service request, such as the level ofurgency, the required timeframe for commencement and completion of theservice, the location of the building, the specific components that areimplicated in the building issue, and other appropriate information.

The other party computing device 408 can receive and output informationabout the service request (452), and can receive input from one or moreusers regarding the service request, such as an acceptance of theservice request and other pertinent details (e.g., price information,current geographic location of the assigned worker, estimated time workwill commence, estimate time when work will be completed,availability/accessibility of components and/or tools needed to completethe service request) regarding the other party fulfilling the servicerequest (454). The other party computing device 408 can transmit theacceptance of the service request and the associated information to thecomputer system 406, and can also transmit updates to that originalinformation (e.g., acceptance, associated information) as they becomeavailable (456). For example, updates to the current schedule andgeographic location of the worker assigned to the service request can beprovided to the computer system 406 so that the computer system 406 canaccurately inform the building owner of the estimated time of arrivalfor the worker.

The computer system 406 receives the acceptance of the service request,the associated information, and updates from the other party computingdevice 408 (458), and transmits information about the service request tothe building owner computing device 402 (460). The information that istransmitted can include a variety of details regarding the servicerequest, such as an identity of the other party, reviews and ratinginformation for the other party, an estimated time when the other partywill arrive at the building, an estimated time to resolve the buildingissue, the determined level of urgency for the issue, instructions onactions for the building owner to take to mitigate further damage and/orto ensure safety of the building's occupants, whether the issue iscovered under warranties or insurance policies, and cost estimates toresolve the building issue. The building owner computing device 402receives and outputs the service request information (462).

The other party that is associated with the other party computing device408 begins working on the service request (464), which can be indicatedto the computer system 406 through status updates provided by the otherparty computing device 408. Upon completion of the service request, theother party computing device 408 can transmit confirmation that theservice request has been completed along with details regarding the workperformed, such as actions taken by the worker, specific components thatwere repaired and/or replaced, the duration of the service request, andother appropriate details (466).

The computer system 406 can receive the confirmation and request furtherconfirmation from the building owner that the work has been completed(468). The building owner computing device 402 can receive the requestfor further confirmation (470) and, in response to user input (e.g.,selecting a button confirming that the work was performed, providing anelectronic signature), can transmit confirmation back to the computersystem 406 (472). In response to receiving the confirmation from thebuilding owner computing device 402, the computer system 406 can updatedata associated with the service request and can process payment for thework based, at least in part, on the actual work performed and anywarranty/insurance coverage for the issue (474). A variety of data canbe updated in association with the service request, such as dataassociated with the building (e.g., information regarding componentsthat are installed in the building), the service request (e.g., updateinformation regarding the work performed as part of the servicerequest), and the building owner and other party (e.g., updateinformation indicating that the building owner and other party were bothassociated with the service request).

FIGS. 5A-Q are screenshots 500 a-q of an example mobile app that can beused by field service providers, such as builders, contractors, vendors,and other service providers. Such a mobile app can be similar to themobile applications 330 and 348 discussed above with regard to FIG. 3,and can be implemented on one or more appropriate computing devices,such as the computing devices 142, 306 and 308.

Such a mobile app can provide a variety of features, which are depictedacross the screenshots 500 a-q. For example, such a mobile app canprovide real-time updates in a dashboard to users; can create, assign,and update work orders with minimal input and effort (e.g., single touchwork order processing) from users; can perform automatic and dynamicscheduling for work orders to more efficiently process service requests,such as through the use of current geographic locations for both workersand service requests; can incorporate location information with eachservice request; can provide instant access to all resources related toservice requests, such as photos, videos, and documentsdescribing/depicting the building issue; and can provide offline accessto all useful information when internet access is not available.

Referring to FIG. 5A, the screenshot 500 a depicts an example loginscreen for a field service provider.

Referring to FIG. 5B, the screenshot 500 b depicts an example dashboardscreen for a field service provider. The dashboard can include anotification area 502 in which notifications for service requests can bedisplayed, such as upcoming scheduled service appointments, new servicerequests, and urgent service requests. The dashboard also includesservice order overview feature 504 in which the user can see the statusof various service orders that are pending. A variety of categories canbe used in the feature 504, including new work orders, work orders inprocess, started work orders, assigned work orders, and accepted workorders. The work orders can be broken down further, such as intoemergency orders and preventative maintenance orders, and based onwhether the orders are nearby the user's current geographic location.

Referring to FIG. 5C, the screenshot 500 c depicts that real-timesyncing, such as through services like JavaScript Object Notation (JSON)web services, can be used to sync information between the backend serversystem (e.g., computer system 102, computer system 302) and the mobileapp. Any and all information that is used by the mobile app can besynced, such as the information that is displayed in the notificationarea 502. Syncing can occur at regular intervals whenever an internetconnection is available to the device, such as every 5 seconds, every 10seconds, every 30 seconds, every minute, every 5 minutes, every 15minutes, and/or other appropriate time intervals.

Referring to FIG. 5D, the screenshot 500 d depicts a schedulinginterface through which real-time schedule and status information forwork orders can be viewed. Schedules can be customized in a variety ofways, such based on whether the work orders are for preventativemaintenance or emergencies.

Referring to FIG. 5E, the screenshot 500 e depicts a status feature 506that is part of the scheduling interface through which a user candesignate the status of a work order. In the depicted example, the usercan designate that an order has been accepted by a worker, that a workeris en route to the call, that the work is in process, that the work hasbeen suspended, and that the work has been cancelled. Status icons 508are presented with the orders to indicate the current status of theorders.

Referring to FIG. 5F, the screenshot 500 f depicts a priority feature510 that is part of the scheduling interface through which a user candesignate the priority/urgency of a work order. In the depicted example,the user can designate that an order has either a low, medium, or highlevel of priority. Status icons 512 are presented with the orders toindicate the priority level of the orders.

Referring to FIG. 5G, the screenshot 500 g depicts a detailed view of anexample work order, which includes a variety of details regarding theorder, such as the equipment that is at issue, the dates on which theorder was received, the location of the work order, and the contactinformation for the user. Detailed views of work orders can be accessedby selecting individual work orders from a variety of other interfaces,such from the notification area 502 and/or the scheduling interfacedepicted in FIGS. 5D-F.

Referring to FIG. 5H, the screenshot 500 h depicts a component list 514for the work order being expanded as part of the view of the work order.The component list 514 is depicted as being collapsed in the screenshot500 g. The component list 514 provides specific information about thecomponents that are in need of being serviced as part of the work order,including specific product names, product numbers, serial numbers,status information, and cost information.

Referring to FIG. 5I, the screenshot 500 i depicts a user havingselected a first component 516 from the component list 514. The user isthen provided with a set of options 518 for the selected component 516.

Referring to FIG. 5J, the screenshot 500 j depicts a user havingselected the “item serviced” option 520 from the set of options 518 forthe selected component 516. Selection of this option 520 causes moredetailed information about the component 516 to be displayed in the itemserviced area 522, which includes a picture of the item, a history ofthe item (e.g., install date, service history) as it pertains to thespecific work order, and information (e.g., error code, problemdescription) about the issue that is being experienced with thecomponent.

Referring to FIG. 5K, the screenshot 500 k depicts the user havingselected the “time start/end” option 526 from the set of options 518 forthe selected component 516. Selection of this option 526 causes a timestart/end interface 524 to be displayed, through which a user candesignate a start date/time and end date/time for when the service forthat specific component 516 was performed.

Referring to FIG. 5L, the screenshot 500 l depicts a list of selectableand viewable resources (e.g., videos, images, training manuals, PDFs)that are available for the user to access. Such resources can beaccessed by workers to learn about how to use the mobile app and/or howto perform various service-related work, such as repairing or replacinga specific component. The list of resources can be presented to a userhaving selected the “resources” option 528 from the set of options 518for the selected component 516. In such a situation, the list ofresources can be related to the selected component 516 and theissue/problem with the selected component 516 that is the reason for thework order. In some implementations, the list of resources may includeresources (e.g., photos, videos) provided by a building owner in regardto an issue with a component.

Referring to FIG. 5M, the screenshot 500 m depicts an example documentresource being presented on the mobile computing device and to the user,such as in response to the user selecting an entry for the documentresource from the list of resources depicted in screenshot 500 l.

Referring to FIG. 5N, the screenshot 500 n depicts an example videoresource being presented on the mobile computing device and to the user,such as in response to the user selecting an entry for the videoresource from the list of resources depicted in screenshot 500 l.

Referring to FIGS. 5000-Q, the screenshots 500 o-q depict example userinterfaces through which payments from users can be processed, includingby credit card, check, and cash, and through the use of electronicsignatures.

FIGS. 6A-H are example screenshots 600 a-h of an example mobileapplication that can be used to address building issues. The exampleapplication can run on a mobile computing device that is associated witha building owner, such as the computing device 124 that is associatedwith the building owner 110 and/or the building owner computing device304. The screenshots in FIGS. 6A-H depict an example sequence of screensthough which the building owner could address issues related to one ormore components/systems (e.g., fire sprinkler systems) that areinstalled in a building, including submitting building issues andsetting up service appointments.

In the screenshot 600 a depicted in FIG. 6A, categories of buildingcomponents/systems that are installed within a user's building arepresented to the user. The categories can be specifically selected basedon the specific components/systems that are installed within a buildingthat is associated with the user. For example, the categories maybroadly cover different categories of components within the building,such as electrical, plumbing, HVAC, fire sprinkler, appliances, and lowvoltage systems. Such categories may be nested and allow the user toselect further subcategories. An example grouping of categories andsubcategories is provided below in Table 1.

TABLE 1 Category Sub-Categories Landscaping Trees Sod Irrigation SystemPaving - driveway Concrete Exterior concrete - sidewalks and garage slabInterior - foundation and basement slab Masonry Wood Framing MillworkCabinets Finish Carpentry Roofing Caulking Insulation Siding GarageDoors Entry Doors Windows Doors and Hardware Gypsum Board CracksAcoustical Textures Tile Flooring Wood Flooring Resilient FlooringCarpet Paint Shower Door and Bathroom Accessories Fireplace KitchenAppliances Garbage Disposal Stove Refrigerator Dishwasher MicrowaveCategory Sub-Categories Kitchen hood Washer Dryer Plumbing Faucet sets -bathroom, kitchen Toilets Hot water heater Sinks Interior sewer Waterlines Hose bibbs Sump pump Fire Sprinkler System HVAC Furnace HRV Air toAir Exchanger Bath Fans A/C Grilles and registers Thermostat Low VoltageSecurity System Home Theater System Cable/TV Hook-Ups Electrical Lightfixtures Outlets Wall switches Door bell Exterior outlets Exterior lightfixtures

In some implementations, each of the categories of buildingcomponents/systems that are installed within a user's building can berepresented by a different selectable button. In the screenshot 600 a,for example, the user can select between air conditioning, ceiling fan,electrical, fire extinguisher, fire sprinkler system, heating, as wellas others that can be selected through scrolling down, but which are notdepicted in the screenshot. The screenshot 600 a further depicts aprofile option 602, a contact option 604, and a help option 606. Theuser can select the profile option 602 to review and modify informationabout his/her account, such as the user's contact information,associated buildings, and billing information. The user can select thecontact option 604 to contact a representative of the system, toregister an emergency with the system and/or to place a call with anemergency response system (e.g. 911 system). The help option 606 can beselected to obtain further annotation about how to use the interfacedepicted in the screenshot 600 a. In response to the user selecting thefire sprinkler system option (e.g., touch-based selection of the firesprinkler system button, voice-based input selecting the fire sprinklersystem option), user interfaces providing information about the specificfire sprinkler system that is installed in the building, its componentparts, and warranty coverage can be presented, as depicted in FIGS.6B-D.

As depicted in the screenshot 600 b of FIG. 6B, for example, buttonsrepresenting component parts of the fire sprinkler system are shown,including fire sprinklers, smoke detectors, and control panels. Inresponse to the user selecting a component (e.g., touch-based selectionof a button representing fire sprinklers, voice-based input selectingthe fire sprinkler option), further options can be presented to assistthe user with troubleshooting the selected component.

Referring to FIG. 6C, the example screenshot 600 c is depicted after theuser has selected a component (e.g., the fire sprinkler component), asindicated by an icon 610 associated with the selected componentappearing in the upper right corner of the screenshot 600 c. Otherfeatures are depicted in the screenshot 600 c, including a warrantyoption 612, which the user can select to view warranty information forthe selected component; a coverage option 614, which the user can selectto view coverage of the selected component; a troubleshoot option 616,which the user can select to troubleshoot a resolution to the issuethemselves; and a service call option 618, which the user can select todirectly place a service call.

In some implementations, the screenshot 600 c may include a questionthat can be part of a series of questions to assess the issue and tohelp determine whether the user should place a service call for theissue to be resolved. For example, upon selecting the troubleshootoption 616, the user can be presented with a question (e.g., “Did youreplace the battery?”) and prompts for input (e.g., yes/no) forresolving issues for the selected component. In response to receivinginput from the user in regard to the question, one or more follow-upquestions (e.g., “Is the warning indicator on?”) or possible solutions(e.g., “Replace the battery by removing the front panel.”) for resolvingissues can be provided.

Referring to FIG. 6D, the example screenshot 600 d is depicted after theuser has selected the warranty option 612. For example, the user can beprovided with information about the current warranty coverage (e.g.,warranty coverage set to expire on Oct. 15, 2015) for the selectedcomponent. In some implementations, selectable options may be providedto renew the warranty coverage through the application. Referring to thescreenshot 600 d, for example, the user can “click here” to extendwarranty service, or can elect to delay renewal.

In response to selection of the service call option 618 in FIG. 6C, theuser can be presented with a user interface through which the user cantriage the issue with the selected component (e.g., fire sprinkler), asdepicted in the screenshots 600 e-h of FIGS. 6E-H. For instance, asdepicted in the screenshot 600 e of FIG. 6E, the user is provided withselectable features 620 to identify the issue that is being experiencedwith the fire sprinkler. The features 620 that are presented in FIG. 6Ecan be populated based on a variety of factors, such as the specificcomponents of the fire sprinkler system, historical issues with thesecomponents (e.g., issues identified through other service inquiriesand/or warranty claims), historical issues associated with firesprinkler systems installed and/or serviced by one or more contractorswho have worked on the user's system (e.g., history of the contractornot properly installing particular components that later fail), and/orother appropriate factors. The screenshot 600 e, for example, includesfeatures 620 through which a user can further specify the issues thatthey are experiencing with the fire sprinkler, an upload image button622 through which the user can select one or more images to provide thatdepict the issue with the fire sprinkler, an upload video button 624through which the user can select one or more videos to provide thatdepict the issue with the fire sprinkler, a desired appointment button626 through which the user can designate one or more days and times thatwould work best for an appointment, and an additional comment button 628through which the user can provide additional information regarding theissue. Confirmation of appointments can be provided after a serviceprovider confirms a time that will work with his/her schedule, which canbe synced through one or more calendar programs, such as MICROSOFTEXCHANGE and GOOGLE CALENDAR.

As depicted in the screenshot 600 f of FIG. 6F, the user can upload oneor more images of the issue, such as by selecting an image from a localor remote file system (e.g., local photo album, remote photo album,email attachment, image transmitted through MMS message) and/or bytaking photos using one or more cameras on the device (e.g., frontand/or rear facing cameras on a smartphone and/or tablet computingdevice). Similarly, the user can upload one or more videos that depictthe issue, such as through selection of videos from a local or remotefile system (e.g., local video repository, remote video repository,email attachment, video transmitted through MMS message) and/or bytaking videos using one or more cameras and microphones on the device(e.g., front/rear facing cameras and embedded microphones that are partof smartphones and/or tablet computing devices).

As depicted in the screenshot 600 g of FIG. 6G, the user can enter andupload additional comments regarding the issue, and, as depicted in thescreenshot 600 h of FIG. 6H, the user can select a desired appointmentdate and/or time for the service call. In some implementations,confirmations/reminders may be provided for a scheduled appointment. Forexample, such a reminder can be provided at a predetermined amount oftime before the appointment, such as 1 week before, 3 days before, 1 daybefore, 6 hours before, 2 hours before, 1 hour before, and/or otherpredetermined time periods.

In some implementations, the example mobile application that can be usedto address building issues may include an interface through a user canlogin to the system (e.g., computer system 102, computer system 302)from a mobile computing device. For example, the user can enter ausername and password. Other possible ways of authenticating a user onthe mobile computing device, such as a smartphone, are also possible,such as fingerprint verification, facial recognition, voice recognition,retinal scans, biometic verification, and/or other appropriate loginmechanisms.

In some implementations, the example mobile application that can be usedto address building issues may include an interface through which theuser can provide his/her signature to verify that the work has beencompleted, and through which the user can review and/or rate the workperformed by the contractor/developer. For example, the interface may bepresented on the user's mobile computing device after thecontractor/developer has sent a confirmation to the system (e.g., system102, system 302) that the work has been completed through their owncomputing device.

Other features can also be provided through the interfaces depicted inthe screenshots 600 a-h, such as an area in which a user can be notifiedof recalls on the specific components that are installed in one or moreof the user's buildings. For example, a tab or button could be providedin the interface depicted in screenshot 600 c in which a user can benotified of a number of components that currently have outstandingrecall notices, which may originate from any of a variety of parties(e.g., manufacturers, service providers, warranty providers, insurers).A backend computer system, such as the computer systems 102, 302, and/or406, can identify and notify users of such recalls. For example, suchbackend computer systems can receive and/or obtain information aboutcomponent recalls (e.g., monitor recall notices provided bymanufacturers, receive notification from manufacturers), can comparerecall information (e.g., component make and model number, serialnumber) to component information for buildings, can identify componentsthat are subject to one or more recalls, and can push/send notificationsof such recalls to users. Such notifications can include any of avariety of appropriate details, such as information identifying thespecific components that is being recalled, the reason for the recall,any danger/risk that may be posed by the component until it isreplaced/repaired, and/or steps that the user should take to mitigatesuch danger/risk. The notification can also provide the user with anoption to schedule a service call to address the recall, similar to theprocesses described above with regard to automating service requests.

Although not explicitly described or depicted above with regard to FIGS.1-4, the computer systems 102, 302, and/or 406 can additionally beprogrammed to process payments for things that are authorized by endusers, such as payment authorizations provided by the building owner 110through the computing device 124, payment authorizations provided by theother party 112 through the computing device 142, authorizationsprovided through the computing devices 304-306, 402, 404, and 408, andauthorizations provided through the interfaces depicted in thescreenshots 500 a-q and 600 a-h. The computer systems 102, 302, and/or402 may include one or more ecommerce modules that are configured toprocess electronic payments, such as credit card payments, electronicfunds transfers (EFTS), and/or other electronic payments (e.g., APPLEPAY). The computer systems 102, 302, and/or 402 may also be configuredto process payments through communication with one or more third-partyelectronic payment processing systems, such as those provided by PAYPAL,SQUARE, and APPLE PAY.

For example, in response to user selection of an option to renew awarranty that will expire shortly, the mobile computing device that isdepicted in screenshot 600 d can send the payment authorization to acorresponding backend computer system (e.g., the computer systems 102,302, and 402), which can process the electronic payment and, once theelectronic payment has been successfully made, can renew/extend theperiod of the warranty. Such electronic payments can be made from clientdevices for any of a variety of other services as well, such aspurchasing products (e.g., components, consumer products), services(e.g., paying for repair services that may not be covered by insuranceor warranties), and/or paying for a subscription to use the services ofthe computer system (e.g., renewing a subscription with the computersystems 102, 302, and 402).

FIG. 7 is a diagram of an example workflow 700 for an entity withmultiple different departments that are used by the entity to scheduleand provide services to customers. The operations that are part of theexample workflow 700 are depicted as being performed by a customer 702,a front office 704, a back office 706, operations 708, and finance 710.The front office 704, the back office 706, the operations 708, andfinance 710 can all be different departments/groups/roles within anorganization, such as a contractor/builder/service provider.

The operations that are performed by the customer 702 can be performedon a computing device that is associated with the customer 702, such asthe computing device 124, the computing device 304, and/or the mobilecomputing device that is depicted in FIGS. 6A-H.

The operations that are performed across 704-710 can all be performed onthe same computing device or across multiple different computingdevices, which may each have separate application (e.g., mobile apps,desktop applications) with specific functionality needed for each role.For example, the operations of the front office 704 can be performed bysalesmen and customer service representatives using specificallydesigned applications to perform the operations listed for the frontoffice 704, such as creating service requests that will be fulfilled byoperations 708. Operations 708 can use an application, which may be thesame as or different from the application for the front office 704, todirect their execution of service requests and other associated tasks.The back office 706 can be responsible overseeing and managing both thefront office 704 and the operations 708, and can use applications (sameor different from applications used by the front office 704 andoperations 708) to perform scheduling and service agreement operations.The finance 710 can additionally use an application (same or differentfrom the applications used by others) to manage money flow andaccounting within the entity.

The applications that are used by 704-710 can be run on any of a varietyof appropriate computing devices, such as computing devices 142, 306,308, and/or the computing device depicted in FIGS. 5A-Q.

FIG. 8 is an architectural diagram 800 of a mobile application andsupporting backend system for field service providers, such as builders,contractors, vendors, and other service providers.

The mobile application (e.g., IPAD app) depicted in the diagram 800 canprovide a variety of features that are used by field service providers,such as scheduling and dispatch of workers (e.g., field serviceproviders), route optimization for workers responding to servicerequests, warranty management, inventory and parts logistics forcomponents that are used in service requests and new installations,offline access to all resources, and a document repository (e.g., workorders, training documents). The mobile application can be provided onany of a variety of appropriate computing devices, such as the computingdevices 142, 306, 308, and/or the computing device depicted in FIGS.5A-Q.

The supporting backend system can include a middleware layer thatprovides database support and web services that are used by the mobileapplication, such as services that are provided through one or moreappropriate data sources (e.g., customer resource management (CRM)systems, SAP systems, DMS systems). The backend system can additionallyinclude a management console through which information about theperformance and state of the backend system can be viewed. Thesupporting backend system can be provided by any of a variety ofappropriate computer systems, such as the computer systems 102 and 302.

The technology described above can additionally or alternatively includeone or more of the following features. Data that is obtained fromservice requests can be used to provide useful analytics to a variety ofparties, such as builders, contractors, manufacturers, warrantyproviders, and insurers. For example, builders would be interested infinding out what components work well and raise few issues for homeowners, and what components do not work well and raise many issues forhome owners. In the aggregate, the data points collected from servicerequests can provide a builder with insight into the specific componentsthat they install in homes, as well as a broader view of componentsinstalled by other builders. For instance, from such analytics a buildermay learn that a particular component frequently causes issues forhomeowners, but that a competitor component that is installed by otherbuilders and that provides the same functionality has a much lower rateof incident. This may prompt the builder to switch to using thecompetitor component. In another instance, a builder may learn that fora particular component the builder has a greater rate of incident thanother builders installing the same component. This may prompt thebuilder to check that the component is being installed properly by thebuilder's workers and that the homeowners are being properly educationon how to use and maintain the component.

In another example, data points collected from service requests canprovide manufacturers with greater levels of detail as to when and inwhat situations their products are either malfunctioning or are causinghomeowners to incorrectly believe that they are malfunctioning. Suchinsight can help manufacturers improve product designs and educationalmaterial to avoid such instances.

In a further example, warranty providers and insurers can obtain greaterinsight into costs and probabilities of malfunction with particularcomponents. Such insight may allow warranty providers and insurers tomore appropriately price policies based on factors related to componentinstallation, such as the climate where the component is beinginstalled, the identity of workers who are installing the components,and/or other relevant factors.

Such analytics information can be provided using any of a variety ofappropriate techniques to ensure accuracy of the data and, whereappropriate, anonymity of the parties involved in the specific instancesthat are aggregated together. Analytics information can be licensedunder any of a variety of pricing structures, such assubscription-bases.

In another example, the mobile apps and webpages that are described asbeing provided for building owners (e.g. homeowners) can includemaintenance checklists for users to perform on the specific componentsthat are installed in their building. Such checklists can track whenmaintenance is performed and information about such maintenance can belogged in association with the building. The checklists feature canprovide the user with reminders about upcoming maintenance, instructionsas to how to perform the maintenance, and features through which userscan submit a service request for a professional to perform themaintenance. Incentives may be tied to performance of one or moremaintenance items on the checklist, such as lower warranty renewal rateswhen suggested maintenance is performed on a component according to thesuggested maintenance schedule.

In a further example, the technology disclosed above may communicatewith and obtain information directly from components within a building.For instance, many components in a building, such as thermostats,appliances, and light fixtures, are capable of communicating andproviding status information over one or more communication networks,such as Wi-Fi. The disclosed technology can allow for a user's computingdevice to be in communication with such components in the user'sbuilding and can flag potential issues for the user automatically when apossible malfunction has been detected. In some instances, a user may berequired to verify and/or consent to a service request being sent out toa computer system (e.g., the computer system 102, the computer system302). In other instance, a user's computing device may automaticallytransmit a service request to a computer system when any issue or issueswith at least a threshold level of severity are detected.

Computing devices and computer systems described in this document thatmay be used to implement the systems, techniques, machines, and/orapparatuses can operate as clients and/or servers, and can include oneor more of a variety of appropriate computing devices, such as laptops,desktops, workstations, servers, blade servers, mainframes, mobilecomputing devices (e.g., PDAs, cellular telephones, smartphones, and/orother similar computing devices), computer storage devices (e.g.,Universal Serial Bus (USB) flash drives, RFID storage devices, solidstate hard drives, hard-disc storage devices), and/or other similarcomputing devices. For example, USB flash drives may store operatingsystems and other applications, and can include input/output components,such as wireless transmitters and/or USB connector that may be insertedinto a USB port of another computing device.

Such computing devices may include one or more of the followingcomponents: processors, memory (e.g., random access memory (RAM) and/orother forms of volatile memory), storage devices (e.g., solid-state harddrive, hard disc drive, and/or other forms of non-volatile memory),high-speed interfaces connecting various components to each other (e.g.,connecting one or more processors to memory and/or to high-speedexpansion ports), and/or low speed interfaces connecting variouscomponents to each other (e.g., connecting one or more processors to alow speed bus and/or storage devices). Such components can beinterconnected using various busses, and may be mounted across one ormore motherboards that are communicatively connected to each other, orin other appropriate manners. In some implementations, computing devicescan include pluralities of the components listed above, including aplurality of processors, a plurality of memories, a plurality of typesof memories, a plurality of storage devices, and/or a plurality ofbuses. A plurality of computing devices can be connected to each otherand can coordinate at least a portion of their computing resources toperform one or more operations, such as providing a multi-processorcomputer system, a computer server system, and/or a cloud-based computersystem.

Processors can process instructions for execution within computingdevices, including instructions stored in memory and/or on storagedevices. Such processing of instructions can cause various operations tobe performed, including causing visual, audible, and/or hapticinformation to be output by one or more input/output devices, such as adisplay that is configured to output graphical information, such as agraphical user interface (GUI). Processors can be implemented as achipset of chips that include separate and/or multiple analog anddigital processors. Processors may be implemented using any of a numberof architectures, such as a CISC (Complex Instruction Set Computers)processor architecture, a RISC (Reduced Instruction Set Computer)processor architecture, and/or a MISC (Minimal Instruction Set Computer)processor architecture. Processors may provide, for example,coordination of other components computing devices, such as control ofuser interfaces, applications that are run by the devices, and wirelesscommunication by the devices.

Memory can store information within computing devices, includinginstructions to be executed by one or more processors. Memory caninclude a volatile memory unit or units, such as synchronous RAM (e.g.,double data rate synchronous dynamic random access memory (DDR SDRAM),DDR2 SDRAM, DDR3 SDRAM, DDR4 SDRAM), asynchronous RAM (e.g., fast pagemode dynamic RAM (FPM DRAM), extended data out DRAM (EDO DRAM)),graphics RAM (e.g., graphics DDR4 (GDDR4), GDDRS). In someimplementations, memory can include a non-volatile memory unit or units(e.g., flash memory). Memory can also be another form ofcomputer-readable medium, such as magnetic and/or optical disks.

Storage devices can be capable of providing mass storage for computingdevices and can include a computer-readable medium, such as a floppydisk device, a hard disk device, an optical disk device, a Microdrive,or a tape device, a flash memory or other similar solid state memorydevice, or an array of devices, including devices in a storage areanetwork or other configurations. Computer program products can betangibly embodied in an information carrier, such as memory, storagedevices, cache memory within a processor, and/or other appropriatecomputer-readable medium. Computer program products may also containinstructions that, when executed by one or more computing devices,perform one or more methods or techniques, such as those describedabove.

High speed controllers can manage bandwidth-intensive operations forcomputing devices, while the low speed controllers can manage lowerbandwidth-intensive operations. Such allocation of functions isexemplary only. In some implementations, a high-speed controller iscoupled to memory, display 616 (e.g., through a graphics processor oraccelerator), and to high-speed expansion ports, which may acceptvarious expansion cards; and a low-speed controller is coupled to one ormore storage devices and low-speed expansion ports, which may includevarious communication ports (e.g., USB, Bluetooth, Ethernet, wirelessEthernet) that may be coupled to one or more input/output devices, suchas keyboards, pointing devices (e.g., mouse, touchpad, track ball),printers, scanners, copiers, digital cameras, microphones, displays,haptic devices, and/or networking devices such as switches and/orrouters (e.g., through a network adapter).

Displays may include any of a variety of appropriate display devices,such as TFT (Thin-Film-Transistor Liquid Crystal Display) displays, OLED(Organic Light Emitting Diode) displays, touchscreen devices, presencesensing display devices, and/or other appropriate display technology.Displays can be coupled to appropriate circuitry for driving thedisplays to output graphical and other information to a user.

Expansion memory may also be provided and connected to computing devicesthrough one or more expansion interfaces, which may include, forexample, a SIMM (Single In Line Memory Module) card interfaces. Suchexpansion memory may provide extra storage space for computing devicesand/or may store applications or other information that is accessible bycomputing devices. For example, expansion memory may includeinstructions to carry out and/or supplement the techniques describedabove, and/or may include secure information (e.g., expansion memory mayinclude a security module and may be programmed with instructions thatpermit secure use on a computing device).

Computing devices may communicate wirelessly through one or morecommunication interfaces, which may include digital signal processingcircuitry when appropriate. Communication interfaces may provide forcommunications under various modes or protocols, such as GSM voicecalls, messaging protocols (e.g., SMS, EMS, or MMS messaging), CDMA,TDMA, PDC, WCDMA, CDMA2000, GPRS, 4G protocols (e.g., 4G LTE), and/orother appropriate protocols. Such communication may occur, for example,through one or more radio-frequency transceivers. In addition,short-range communication may occur, such as using a Bluetooth, Wi-Fi,or other such transceivers. In addition, a GPS (Global PositioningSystem) receiver module may provide additional navigation- andlocation-related wireless data to computing devices, which may be usedas appropriate by applications running on computing devices.

Computing devices may also communicate audibly using one or more audiocodecs, which may receive spoken information from a user and convert itto usable digital information. Such audio codecs may additionallygenerate audible sound for a user, such as through one or more speakersthat are part of or connected to a computing device. Such sound mayinclude sound from voice telephone calls, may include recorded sound(e.g., voice messages, music files, etc.), and may also include soundgenerated by applications operating on computing devices.

Various implementations of the systems, devices, and techniquesdescribed here can be realized in digital electronic circuitry,integrated circuitry, specially designed ASICs (application specificintegrated circuits), computer hardware, firmware, software, and/orcombinations thereof. These various implementations can includeimplementation in one or more computer programs that are executableand/or interpretable on a programmable system including at least oneprogrammable processor, which may be special or general purpose, coupledto receive data and instructions from, and to transmit data andinstructions to, a storage system, at least one input device, and atleast one output device.

These computer programs (also known as programs, software, softwareapplications, or code) can include machine instructions for aprogrammable processor, and can be implemented in a high-levelprocedural and/or object-oriented programming language, and/or inassembly/machine language. As used herein, the terms “machine-readablemedium” “computer-readable medium” refers to any computer programproduct, apparatus and/or device (e.g., magnetic discs, optical disks,memory, Programmable Logic Devices (PLDs)) used to provide machineinstructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., LCD display screen, LED display screen) for displayinginformation to users, a keyboard, and a pointing device (e.g., a mouse,a trackball, touchscreen) by which the user can provide input to thecomputer. Other kinds of devices can be used to provide for interactionwith a user as well; for example, feedback provided to the user can beany form of sensory feedback (e.g., visual feedback, auditory feedback,and/or tactile feedback); and input from the user can be received in anyform, including acoustic, speech, and/or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), peer-to-peernetworks (having ad-hoc or static members), grid computinginfrastructures, and the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

The above description provides examples of some implementations. Otherimplementations that are not explicitly described above are alsopossible, such as implementations based on modifications and/orvariations of the features described above. For example, the techniquesdescribed above may be implemented in different orders, with theinclusion of one or more additional steps, and/or with the exclusion ofone or more of the identified steps. Additionally, the steps andtechniques described above as being performed by some computing devicesand/or systems may alternatively, or additionally, be performed by othercomputing devices and/or systems that are described above or othercomputing devices and/or systems that are not explicitly described.Similarly, the systems, devices, and apparatuses may include one or moreadditional features, may exclude one or more of the identified features,and/or include the identified features combined in a different way thanpresented above. Features that are described as singular may beimplemented as a plurality of such features. Likewise, features that aredescribed as a plurality may be implemented as singular instances ofsuch features. The drawings are intended to be illustrative and may notprecisely depict some implementations. Variations in sizing, placement,shapes, angles, and/or the positioning of features relative to eachother are possible.

1. A computer-implemented method comprising: receiving, at a computersystem and from a client computing device, information that describes anissue with a building, wherein the information includes firstinformation corresponding to the issue and second informationidentifying the building or a user associated with the building, thefirst information included at least (i) issue identification informationthat describes a symptom of the issue observed by a user of the clientcomputing device, (ii) detected location information that identifies alocation within the building at which the symptom of the issue isobserved by the user of the client computing device, and (iii) digitalinformation captured by the client computing device that visuallydepicts the issue; accessing, by the computer system and based on thesecond information identifying the building or the user associated withthe building, data that identifies (i) a plurality of components thatare included in the building and (ii) features of the plurality ofcomponents, wherein the data includes (i) component attributeinformation that identifies one or more of: component types for theplurality of components, ranges of potential issues with the pluralityof components, and common issues with the plurality of components, (ii)component location information that identifies locations within thebuilding where the plurality of components are installed, and (iii)component visual information that depict the plurality of components;and identifying, by the computer system and based on a comparison of thefirst information with the data for the building, one or more candidatecomponents that have at least a threshold likelihood of being, at leastpartially, a cause of the issue, wherein the identifying comprises:determining, by the computer system, issue matching scores for each ofthe plurality of components based on comparisons of the issueidentification information with the component attribute information;determining, by the computer system, location matching scores for eachof the plurality of components based on comparisons of the detectedlocation information with the component location information;determining, by the computer system, visual matching scores for each ofthe plurality of components based on comparisons of the digitalinformation captured by the client computing device with the componentvisual information; and selecting, by the computer system, the one ormore candidate components from among the plurality of components basedon one or more of the issue matching scores, the location matchingscores, and the visual matching scores.
 2. The computer-implementedmethod of claim 1, further comprising: selecting, by the computersystem, a candidate service provider from among a plurality of serviceproviders based on a comparison of the one or more candidate components;transmitting, by the computer system, a service request for the issue tothe candidate service provider; and scheduling, by the computer system,a service appointment with the candidate service provider to resolve theissue.
 3. The computer-implemented method of claim 2, wherein: theservice request includes information identifying the one or morecandidate components, and the response from the candidate serviceprovider indicates that the one or more candidate components arecurrently accessible to the candidate service provider for the serviceappointment.
 4. The computer-implemented method of claim 2, wherein: theservice request includes information identifying a timeframe forresolving the issue, and the response from the candidate serviceprovider indicates that the candidate service provider is currently ableto resolve the issue within the timeframe.
 5. The computer-implementedmethod of claim 4, further comprising: determining a level of urgency ofthe issue based on the information received from the client computingdevice; and determining the timeframe based, at least in part, on thelevel of urgency.
 6. The computer-implemented method of claim 2,wherein: the candidate service provider is selected using a biddingprocess for the service request involved a plurality of candidateservice providers, and the candidate service provider is selected based,at least in part, on a particular bid that was provided by the candidateservice provider for the bidding process.
 7. The computer-implementedmethod of claim 1, wherein the digital information comprises at leastone of one or more photographs taken of the issue by the clientcomputing device, one or more videos taken of the issue by the clientcomputing device, or audio input taken of the issue by the clientcomputing device.
 8. The computer-implemented method of claim 1, whereinthe identifying further comprises: transmitting, by the computer systemand to the client computing device, component information that describesthe one or more candidate components to the client computing device, thecomponent information being received and presented in a user interfaceon the client computing device; and receiving, at the computer systemand from the client computing device, selection of one or more of thecandidate components as being a likely cause of the issue.
 9. Thecomputer-implemented method of claim 8, wherein the componentinformation comprises at least one of images of the one or morecomponents or video of the one or more components.
 10. Thecomputer-implemented method of claim 8, wherein the componentinformation comprises textual description of where in the building theone or more components are installed.
 11. The computer-implementedmethod of claim 1, further comprising: determining whether the one ormore candidate components are covered under one or more warranties; andtransmitting information about the one or more warranties to the clientcomputing device.
 12. The computer-implemented method of claim 2,further comprising: receiving information from the candidate serviceprovider indicating that the issue with the building has been resolved;transmitting, to the client computing device, a request for confirmationthat the issue has been resolved; and receiving, from the clientcomputing device, confirmation that the issue has been resolved.
 13. Thecomputer-implemented method of claim 12, further comprising: in responseto receiving the confirmation from the client computing device,processing a payment of one or more invoices from the candidate serviceprovider for work performed at the service appointment.
 14. A computersystem comprising: one or more computer processors; and a memory storageapparatus in data communication with the one or more processors andstoring instructions executable by the one or more processes and thatupon such execution cause the one or more processors to performoperations comprising: receiving, over the internet from a clientcomputing device, information that describes an issue with a building,wherein the information includes first information corresponding to theissue and second information identifying the building or a userassociated with the building, the first information included at least(i) issue identification information that describes a symptom of theissue observed by a user of the client computing device, (ii) detectedlocation information that identifies a location within the building atwhich the symptom of the issue is observed by the user of the clientcomputing device, and (iii) digital information captured by the clientcomputing device that visually depicts the issue; accessing, based onthe second information identifying the building or the user associatedwith the building, data that identifies (i) a plurality of componentsthat are included in the building and (ii) features of the plurality ofcomponents, wherein the data includes (i) component attributeinformation that identifies one or more of: component types for theplurality of components, ranges of potential issues with the pluralityof components, and common issues with the plurality of components, (ii)component location information that identifies locations within thebuilding where the plurality of components are installed, and (iii)component visual information that depict the plurality of components;and identifying, based on a comparison of the first information with thedata for the building, one or more candidate components that have atleast a threshold likelihood of being, at least partially, a cause ofthe issue, wherein the identifying comprises: determining issue matchingscores for each of the plurality of components based on comparisons ofthe issue identification information with the component attributeinformation; determining location matching scores for each of theplurality of components based on comparisons of the detected locationinformation with the component location information; determining visualmatching scores for each of the plurality of components based oncomparisons of the digital information captured by the client computingdevice with the component visual information; and selecting the one ormore candidate components from among the plurality of components basedon one or more of the issue matching scores, the location matchingscores, and the visual matching scores.
 15. The computer system of claim14, the operations further comprising: selecting a candidate serviceprovider from among a plurality of service providers based on acomparison of the one or more candidate components; transmitting aservice request for the issue to the candidate service provider; andscheduling a service appointment with the candidate service provider toresolve the issue.
 16. The computer system of claim 15, wherein: theservice request includes information identifying the one or morecandidate components, and the response from the candidate serviceprovider indicates that the one or more candidate components arecurrently accessible to the candidate service provider for the serviceappointment.
 17. The computer system of claim 15, wherein: the servicerequest includes information identifying a timeframe for resolving theissue, and the response from the candidate service provider indicatesthat the candidate service provider is currently able to resolve theissue within the timeframe.
 18. The computer system of claim 17, theoperations further comprising: determining a level of urgency of theissue based on the information received from the client computingdevice; and determining the timeframe based, at least in part, on thelevel of urgency.
 19. The computer system of claim 15, wherein: thecandidate service provider is selected using a bidding process for theservice request involved a plurality of candidate service providers, andthe candidate service provider is selected based, at least in part, on aparticular bid that was provided by the candidate service provider forthe bidding process.
 20. The computer system of claim 14, wherein thedigital information comprises at least one of one or more photographstaken of the issue by the client computing device, one or more videostaken of the issue by the client computing device, or audio input takenof the issue by the client computing device.